Connection device restriction program and device

ABSTRACT

A connection device restriction program for preventing use of uncalled-for connection devices. A permission list setting unit sets a connection permission list holding information defining connection devices whose connection is to be permitted, and a list memory stores the connection permission list. When a connection device is connected to one of first to third connection ports, a connection restriction unit acquires device information from the connection device, and collates the device information with the connection permission list to determine whether or not the connection device corresponds to any one of the connection-permitted devices. If the connection device corresponds to any one of the connection-permitted devices, connection of the device is permitted; if not, connection of the device is forbidden.

CROSS-REFERENCE TO RELATED APPLICATIONS

This is a Divisional of application Ser. No. 11/088,435, filed Mar. 24,2005.

This application is based upon and claims the benefits of priority fromthe prior Japanese Patent Application No. 2004-378611, filed on Dec. 28,2004, the entire contents of which are incorporated herein by reference.

BACKGROUND OF THE INVENTION

1. Field of the Invention

The present invention relates to connection device restriction programand device, and more particularly, to a program and device forrestricting use of connection devices connected to a computer.

2. Description of the Related Art

Computers used in offices and homes, for example, personal computers(hereinafter PCs), have a built-in function of automatically installingdevice drivers and making necessary settings when peripheral devices orexpansion cards (hereinafter referred to generically as devices) areconnected. For example, PCs are equipped with connection devices, astypified by USB (Universal Serial Bus), which permit easy connection ofvarious peripheral devices including a keyboard, a mouse, an externalstorage, etc.

A USB device has a built-in function of transmitting information such asdevice type in response to a request from an OS (Operating System),which is basic software, when the USB device is connected to a PC.

FIG. 11 is a flowchart showing a conventional procedure for reading outUSB device information. On receiving a notification that a USB devicehas been connected to a connection port, the OS requests deviceinformation on the connected USB device and extracts target USB deviceinformation (Step S91). The extracted USB device information is thensent to the OS (Step S92). After the USB device information is acquiredin this manner, the OS identifies the device type etc. of the connecteddevice and performs necessary processing to permit use of the connecteddevice. This procedure enables immediate use of a device newly connectedto USB.

However, the ease of connection of peripheral devices poses securityproblems such as a leakage of information from the PC or ingress ofunnecessary information into the PC.

To solve such problems, there have been proposed techniques forrestricting use of peripheral devices according to their categories. Thecategory “storage”, for example, is set, whereupon a storage device, ifconnected, cannot be used.

A connection collation system has also been proposed in which the serialnumbers of connection terminals are registered in a computer, the serialnumber of a connection terminal requesting permission for connection iscollated with the registered serial numbers, and connection of theterminal is permitted only if the serial number of the terminal isregistered (see Unexamined Japanese Patent Publication No. 2003-6166(paragraph nos. [0007] to [0019], FIG. 1), for example).

However, the conventional connection device restriction techniques arepoor in usability because of the inability to allow detailed setting ofrestriction conditions or the need for complicated setting operation,and are associated with a problem that the use of uncalled-forconnection devices cannot be prevented.

Where the use of devices is restricted according to categories, it isnot possible to place restrictions on individual devices separately,since the determination as to restriction is made at a level near theapplication program, namely, at a level where the information on devicesis so abstracted that detailed information on individual devices is notavailable. For example, if restriction is placed on the category“storage”, all storages fail to be connected. A problem also arises inthat restriction can be imposed only on the existing categories.

On the other hand, with the connection collation system in which theserial number of a connection terminal is collated to determine whetherto permit connection of the terminal, it is necessary to register theserial numbers of all terminals whose connection is to be permitted.Thus, if the system is operated on a large scale, the number ofterminals to be registered increases, making the registration workcomplicated and also possibly entailing erroneous registration. Further,the system merely determines whether a terminal may be connected or notand does not allow detailed settings such that a certain terminal ispermitted to read but not to write, for example.

Thus, with the conventional device restriction techniques, restrictionscan only be placed according to existing categories or on individualdevices, and it is not possible to make various restriction settings,such as restrictions on users, makers, products, connection devices tobe used, modes of use, etc. For example, the conventional techniques areunable to cope with a situation where “Mr. A is permitted to use onlythe USB memory with the identification number Z and the product name Y,produced by X Corporation, and is not permitted to use other USBmemories and USB devices.” Accordingly, there is every possibility thatrestriction fails to be imposed in a desired manner or that the settingsare omitted or erroneously made, giving rise to a security problem thatthe use of uncalled-for devices cannot be prevented.

SUMMARY OF THE INVENTION

The present invention was created in view of the above circumstances,and an object thereof is to provide connection device restrictionprogram and device whereby use of connection devices connected to acomputer can be restricted under desired conditions specifying devicetypes, individual devices, users, etc., thereby preventing the use ofuncalled-for connection devices and enhancing security.

To achieve the object, there is provided a connection device restrictionprogram for restricting use of connection devices connected to acomputer. The connection device restriction program causes the computerto execute the step of setting a connection permission list defining aconnection-permitted device which is permitted to connect with thecomputer and storing the connection permission list in a list memory,the step of acquiring device information from a connection device whenthe connection device is connected, the step of collating the acquireddevice information with the connection permission list to determinewhether or not the connection device corresponds to theconnection-permitted device registered in the connection permissionlist, and the step of permitting connection of the connection device ifthe connection device corresponds to the connection-permitted device andotherwise forbidding connection of the connection device.

Also, to achieve the above object, there is provided a connection devicerestriction device for restricting use of connection devices connectedto a computer. The connection device restriction device comprises apermission list setting unit for setting a connection permission listbased on information defining a connection-permitted device which ispermitted to connect with the computer, a list memory for storing theconnection permission list, and a connection restriction unit foracquiring device information from a connection device when theconnection device is connected, collating the acquired deviceinformation with the connection permission list to determine whether ornot the connection device corresponds to the connection-permitted deviceregistered in the connection permission list, and permitting connectionof the connection device if the connection device corresponds to theconnection-permitted device and otherwise forbidding connection of theconnection device.

The above and other objects, features and advantages of the presentinvention will become apparent from the following description when takenin conjunction with the accompanying drawings which illustrate preferredembodiments of the present invention by way of example.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a conceptual diagram illustrating the invention applied toembodiments.

FIG. 2 shows an exemplary arrangement of a connection permission list.

FIG. 3 is a block diagram showing an exemplary hardware configuration ofa PC in which a connection device restriction device according to anembodiment is incorporated.

FIG. 4 is a block diagram exemplifying USB interfaces according to theembodiment.

FIG. 5 shows the arrangement of a USB_DEVICE_DESCRIPTOR.

FIG. 6 is a flowchart showing a USB device connection restrictionprocess according to the embodiment.

FIG. 7 shows the configuration of a connection device restriction deviceof another embodiment which has connection permission lists associatedwith respective user accounts.

FIG. 8 exemplifies a setting tool screen according to the embodiment.

FIG. 9 exemplifies a connection-permitted device registration screenaccording to the embodiment.

FIG. 10 exemplifies an add USB device screen according to theembodiment.

FIG. 11 is a flowchart showing a conventional procedure for reading outUSB device information.

DESCRIPTION OF THE PREFERRED EMBODIMENTS

Preferred embodiments of the present invention will be described belowwith reference to the accompanying drawings. First, the concept of theinvention will be explained, and then specific embodiments to which theinvention is applied will be described.

FIG. 1 is a conceptual diagram illustrating the invention applied to theembodiments.

A connection device restriction device 1 according to the presentinvention is located on the route of information flow between a softwaregroup in a computer, such as OS/drivers 3, and connection ports 2 a, 2 band 2 c to which are connected connection devices (hereinafter devices)as peripheral devices, and controls the data exchange between theOS/drivers 3 and the devices connected to the connection ports 2 a, 2 band 2 c. The connection device restriction device 1 includes a listmemory 1 b for storing a connection permission list 1 a definingconnection-permitted devices (hereinafter permitted devices), apermission list setting unit 1 c for setting the connection permissionlist 1 a, a connection restriction unit 1 d for restricting connectionof devices, and an interface 1 e for controlling the data transferthrough the connection ports 2 a, 2 b and 2 c.

The list memory 1 b stores the connection permission list 1 a and isaccessible from the permission list setting unit 1 c and the connectionrestriction unit 1 d. The connection permission list 1 a containsinformation defining permitted devices whose connection is permitted,that is, information for specifying such permitted devices. The amountof device specification information can be variably set depending on themode of restriction, as described in detail later, and the number ofitems (hereinafter specification items) for specifying a permitteddevice is determined by a target device whose connection is to bepermitted. In the case where the specification items include vendor nameand product name, for example, and a vendor name is specified as aspecification item, connection of the devices with the specified vendorname is permitted. If both a vendor name and a product name arespecified as specification items, connection of the devices with thespecified vendor name and the specified product name is permitted. It isalso possible to make settings so as to permit connection of certaindevice types such as HID (Human Input Device).

The permission list setting unit 1 c acquires information to beregistered in the connection permission list 1 a, sets the acquiredinformation in the connection permission list 1 a, and stores the listin the list memory 1 b. A setting application which urges the user toregister information for creating the connection permission list 1 a maybe stored externally to the permission list setting unit 1 c, and thepermission list setting unit 1 c may be so configured as to receive thecreated connection permission list 1 a and store the list in the listmemory 1 b.

When the connection of a device to one of the connection ports 2 a, 2 band 2 c is detected through the interface 1 e, the connectionrestriction unit 1 d acquires, via the interface 1 e, device informationfor specifying the connected device (Step S1). Then, using the acquireddevice information, the connection restriction unit 1 d collates theconnected device with the permitted devices registered in the connectionpermission list 1 a (Step S2). If the connected device corresponds toany one of the permitted devices registered in the connection permissionlist 1 a, connection of the device is permitted; if not, connection ofthe device is forbidden (Step S3).

The interface 1 e controls the data exchange between the connectionrestriction unit 1 d and devices connected to the connection ports 2 a,2 b and 2 c. Specifically, the interface 1 e transfers informationacquired from the devices to the connection restriction unit 1 d andalso transfers information acquired from the connection restriction unit1 d to the devices.

The aforementioned individual processing units of the connection devicerestriction device 1 are implemented by causing a computer to execute aconnection device restriction program. The processing units mayalternatively be implemented by hardware or by the combination ofhardware and software.

Operation of the connection device restriction device 1 configured asabove will be now described.

Administrator or user registers in advance information defining deviceswhose connection is to be permitted. The permission list setting unit 1c sets the connection permission list 1 a based on the registeredinformation, and stores the list in the list memory 1 b. In theconnection permission list 1 a, information specifying permitteddevices, such as a maker name, a product name, a device serial number,as well as a device type as a whole, can be registered as desired. Forexample, it is possible to specify that “all products from maker X arepermitted”, or “product Y, among those from maker X, is permitted”, or“product Y with serial number Z, among those from maker X, ispermitted.” This makes it possible to place restrictions on use ofdevices in a desired manner such that use of only the specified devicesis permitted or that use of devices is permitted without specifyingindividual devices. Also, instead of specifying individual devices, adevice type as a whole can be specified in a manner such that “HIDdevices of all makers are permitted,” for example. In this case, use ofall HID devices is permitted collectively, and this eliminates the needto make settings for the individual HID devices.

If, after the connection permission list 1 a is stored in the listmemory 1 b, connection of a device to one of the connection ports 2 a, 2b and 2 c is detected through the interface 1 e, the connectionrestriction unit 1 d is notified of the connection of the device. Theconnection restriction unit 1 d acquires device information on theconnected device through the interface 1 e, and collates the acquireddevice information with the connection permission list 1 a to determinewhether connection of the device is permitted or not. If the device isfound to be a permitted device, connection of the device is permitted;if not, connection of the device is forbidden. For example, if theconnection permission list 1 a includes a registration that “allproducts from maker X are permitted” and if the maker of the connecteddevice is X, connection of the device is permitted. Then, the connectionrestriction unit 1 d notifies the OS/drivers 3 of the connection of thedevice and permits the device to be used thereafter. On the other hand,if the maker of the connected device differs from maker X, connection ofthe device is forbidden. In this case, use of the device is forbiddenby, for example, not notifying the OS/drivers 3 of the connection of thedevice.

The connection permission list will be now described with reference toFIG. 2 showing an exemplary connection permission list.

In the illustrated example, the connection permission list has fieldsincluding “DEVICE COUNT” 101 for storing the number of devices set inthe connection permission list, “PERMITTED DEVICE 1” 102 through“PERMITTED DEVICE n” 103 defining respective permitted devices, and“EXCEPTION INFORMATION” 104 defining exceptions.

In the field “DEVICE COUNT” 101 is stored a total number of permitteddevices registered in the connection permission list. Since the totalnumber of registered devices is known from this field, collation withunnecessary fields can be omitted, thereby making the collation processfaster.

In the fields “PERMITTED DEVICE 1” 102 through “PERMITTED DEVICE n” 103is stored information defining respective permitted devices. For eachregistered device, a strength corresponding to permission level isdetermined. The strength indicates the degree of particularization ofthe permitted device. Higher strength requires more specification items,so that the permitted device is specified in further detail. Thespecification items include vendor ID, product ID, and serial number.The vendor ID is a number uniquely assigned to an individual maker foridentifying the maker. The product ID is a number assigned to anindividual product for identifying the product, and the serial number isa number serially assigned to an individual device for specifying thedevice. In the illustrated example, where the strength is low (=1) inwhich the number of specification items is smallest, the vendor ID aloneis specified. Namely, it is possible to enter a registration that “allproducts from maker X are permitted,” for example. In the case of medium(=2) strength with more specification items, the vendor ID and theproduct ID are specified. It is therefore possible to enter aregistration that “product Y, among those from maker X, is permitted,”for example. Where the strength is high (=3) in which individual devicesare specified, the vendor ID, the product ID and the serial number aredesignated as the specification items. Namely, it is possible to enter aregistration that “product Y with serial number Z, among those frommaker X, is permitted,” for example.

In the field “EXCEPTION INFORMATION” 104 is registered informationspecifying a group of devices as a whole, such as device type, to bepermitted or forbidden, and not individual devices as permitted devices.In the illustrated example, the exception information includes itemsrelating to permission of USB hub devices and permission of HID devices.With respect to the item relating to permission of USB hub devices,“ALWAYS PERMIT” is set. This setting is made since use of USB hubs needsto be always permitted in order to control the devices connected to theUSB hubs. For the item relating to permission of HID devices, whetherall HID devices should be forbidden (=0) or permitted (=1) is selectedand set. Thus, whether to permit connection or not can be set withrespect to device types, making it possible to save the time and laborspent on the registration of individual permitted devices. For example,in cases where no problem is expected to result if HID devices areconnected but it is difficult to specify individual makers of HIDdevices that may be used, the exception information 104 may be set asillustrated, whereby use of all HID devices can be permitted with ease.On the other hand, where leak of information to outside should beprevented, connection of storage devices may be forbidden by means ofthe exception information 104, in which case use of all storage devicesis forbidden.

As described above, the connection permission list not only permitsindividual devices to be set as permitted devices but also permitsdevice types to be set collectively as permitted or forbidden devices.Since devices whose connection is to be permitted can be set at desiredpermission levels, the user or administrator can easily create a desiredpermission list matching the use of the computer or the systemconfiguration. Also, the connection device restriction device has onlyto perform substantially the same process (collation of the deviceinformation acquired from a device with the specification items of theregistered permitted devices) regardless of strength level. Further, thespecification items of the connection permission list are set on thebasis of information available from devices, and therefore, therestriction device can deal with conventional devices.

An embodiment of the present invention will be now described in detailwith reference to the drawings wherein the invention is applied to a PCto restrict connection of devices connected to USB ports, by way ofexample.

FIG. 3 is a block diagram showing an exemplary hardware configuration ofa PC in which the connection device restriction device according to theembodiment is incorporated.

The PC 10 is in its entirety under the control of a CPU (CentralProcessing Unit) 11. The CPU 11 is connected, through a bus 19, with aRAM (Random Access Memory) 12, a hard disk drive (HDD) 13, a graphicsprocessor 14, an input interface 15, a communication interface 16, a USBinterface 17, and an IEEE1394 interface 18.

The RAM 12 temporarily stores at least part of the OS and applicationprograms executed by the CPU 11. Also, the RAM 12 stores various otherdata necessary for the processing by the CPU 11. The HDD 13 stores theOS and application programs. The graphics processor 14 is connected witha monitor 21 and, in accordance with instructions from the CPU 11,displays images on the screen of the monitor 21. The input interface 15is connected with a keyboard 22 a and a mouse 22 b, and sends signalsfrom the keyboard 22 a and the mouse 22 b to the CPU 11 through the bus19. The communication interface 16 is connected to a network 23 andtransmits/receives data to/from other devices via the network 23. TheUSB interface 17 is connected, through USB ports, with USB devices 24 aand 24 b, and sends signals from the USB devices 24 a and 24 b to theCPU 11 through the bus 19. Also, in accordance with instructions fromthe CPU 11, the USB interface transmits signals to the USB devices 24 aand 24 b. The USB devices may be of various types including inputdevices such as a scanner, output devices such as a printer, externalmemory, etc. Also, the keyboard 22 a and the mouse 22 b may be connectedvia the USB interface 17. The IEEE1394 interface 18 is connected with anIEEE1394-compliant device and, like the other interfaces, controls thedata exchange between the IEEE1394-compliant device and the CPU 11.

The processing function of the embodiment is accomplished by thehardware configuration described above.

The USB interface will be now described in detail. FIG. 4 is a blockdiagram exemplifying the USB interface according to the embodiment, andin FIG. 4, the other elements of the PC appearing in FIG. 3 are omitted.

The USB interface includes a total of n USB interfaces 17 a, . . . , 17b each connected to the PC via a PCI bus 17 c. Each USB interface, forexample, the USB interface 1 (17 a) has a USB host controller 1 (171 a),a root hub 172 a, and USB ports 176 a and 176 b. Information on devicesconnected to the USB ports 176 a and 176 b is passed on to the root hub172 a and the USB host controller 1 (171 a). The USB port 176 a, whichis provided on the body of the PC, may be connected with USB ports 178 aand 178 b through a hub 177 a. A connection device restriction device173 a includes a connection restriction unit 1731, a list memory 1732storing the connection permission list, and a setting interface 1733.The restriction device 173 a is incorporated in the USB host controller1 (171 a) or the root hub 172 a or is arranged between the two andmanipulates information flowing along the aforementioned route torestrict use of devices. The setting interface 1733 performs the processof acquiring a connection permission list created in accordance with asetting application prepared in the PC and storing the acquired list inthe list memory 1732. The connection restriction unit 1731 acquiresinformation flowing along the above route and, in accordance with theconnection permission list stored in the list memory 1732, permits theinformation to be transferred to the PC side through the PCI bus 17 c ifconnection of the corresponding device is permitted, or forbids theinformation to be transferred to the PC side if connection of thecorresponding device is not permitted. This process will be described indetail later.

Similarly, the USB interface n (17 b) includes a USB host controller n(171 b), a root hub 172 b, and USB ports 176 c and 176 d, and aconnection device restriction device 173 b is incorporated in the USBhost controller n (171 b) or the root hub 172 b or is arranged betweenthe two.

In this manner, the connection device restriction device is located nearthe connection ports through which information flows in from peripheraldevices, to restrict use of the devices.

The connection device restriction device may be provided for each USBport such that the number of restriction devices is equal to that of theUSB ports. This arrangement is, however, very costly as seen from FIG. 4and lacks practicality.

In the following, information obtained from a USB device connected to aUSB port will be explained. According to the USB driver interfacespecification (OpenUSBDI: Open Universal Serial Bus Driver Interface), aUSB device sends a USB_DEVICE_DESCRIPTOR, which is a description of thedevice, in response to a USB device information request from amanagement agent.

FIG. 5 shows the arrangement of the USB_DEVICE_DESCRIPTOR, wherein onlythe part pertaining to the embodiment is extracted.

The USB_DEVICE_DESCRIPTOR has fields including “VENDOR ID” 201, “PRODUCTID” 202, “DEVICE CLASS” 203, “DEVICE SUBCLASS” 204, “SERIAL NO. INDEX”205, etc. In the field “VENDOR ID” 201, a vendor ID determined by theUSB Device Working Group is set. In the field “PRODUCT ID” 202 is set aproduct ID similarly determined with respect to each product. In thefield “DEVICE CLASS” 203, a similarly determined device class code isset, and in the field “DEVICE SUBCLASS” 204, a subclass code is set. Ifthe value in the device class field is “9”, for example, then the devicein question is a USB hub. In the field “SERIAL NO. INDEX” 205 is setinformation indicative of the location of a serial number described inthe ASCII code.

Thus, using the device description information (USB_DEVICE_DESCRIPTOR)obtained from USB devices, the connection permission list is set so asto restrict use of the USB devices.

The process for restricting use of USB devices will be now described. Inconventional techniques, when notified of the connection of a USB deviceto a connection port, the OS requests the description information(USB_DEVICE_DESCRIPTOR) from the connected USB device. Also, in theabove description of the embodiment, when a USB device is connected to aconnection port, the connection device restriction device is notified ofthe connection of the USB device, and if it is judged by the connectiondevice restriction device that connection of the USB device ispermitted, the OS is notified of the connection of the device.Alternatively, a notification indicating the connection of a USB devicemay once be sent to the OS and the response for USB_DEVICE_DESCRIPTOR,generated by the OS, may be used for the purpose of control. Also inthis case, a similar function can be performed.

The following describes the case where the response forUSB_DEVICE_DESCRIPTOR generated by the OS is utilized to restrict use ofdevices. It is assumed that the connection permission list has thearrangement shown in FIG. 2, that higher strength requires morespecification items such as vendor ID, product ID and serial number, andthat the exception information specifies that connection of USB hubdevices is always permitted, and includes permit/forbid setting madewith respect to all HID devices.

FIG. 6 is a flowchart showing a USB device connection restrictionprocess according to the embodiment.

The process is started when a request to acquire theUSB_DEVICE_DESCRIPTOR of a target is received from the OS.

[Step S11] A USB_DEVICE_DESCRIPTOR is acquired from a target USB deviceconnected to the connection port. The USB_DEVICE_DESCRIPTOR includes thevendor ID, product ID, device class and serial number index of thetarget device, as shown in FIG. 5, as well as pointer information usedfor acquiring other information.

[Step S12] The exception information is processed first. It isdetermined whether the target device is a USB hub or not. If the valuein the device class field is “9”, the device is a USB hub. Connection ofUSB hubs is always permitted, as shown in FIG. 2, and therefore, wherethe target device is a USB hub, the process proceeds to Step S18.

[Step S13] If the target device is not a USB hub, aUSB_CONFIGURATION_DESCRIPTOR is additionally acquired from the targetdevice.

[Step S14] It is determined whether or not the exception informationspecifies that connection of HID devices is always permitted, and alsowhether or not the target device is an HID device. If the exceptioninformation indicates that connection of HID devices is alwayspermitted, it is confirmed whether the target is an HID device. If theinterface class field in the USB_INTERFACE_DESCRIPTOR in theUSB_CONFIGURATION_DESCRIPTOR shows the value “3”, then the target deviceis an HID device. If the target is an HID device and also if theexception information specifies that connection of HID devices ispermitted, the process proceeds to Step S18.

[Step S15] If connection of the target is not permitted in the course ofthe exception information check in Steps S12 to S14, the target iscollated with the permitted devices registered in the connectionpermission list. Based on the serial number index in theUSB_DEVICE_DESCRIPTOR, a serial number is acquired from aUSB_STRING_DESCRIPTOR of the target. The vendor ID and the product IDare already acquired from the USB_DEVICE_DESCRIPTOR.

[Step S16] The vendor ID, product ID and serial number of the target arecollated with those of the permitted devices 1 through n registered inthe connection permission list. At this time, the vendor ID alone iscollated if the registered strength level is “1”, the vendor ID and theproduct ID are collated if the strength level is “2”, and all of thevendor ID, product ID and serial number are collated if the strengthlevel is “3”. If the target is found to be a permitted device, theprocess proceeds to Step S18.

[Step S17] If the target is not a permitted device, an errornotification is sent to the OS and the process is ended, whereby the OSregards the target as not operating normally and does not establishconnection therewith. Namely, the target cannot be used. If necessary, amessage to the effect that use of the target device is not permitted maybe displayed on the monitor.

[Step S18] Since the target is a permitted device, the acquiredUSB_DEVICE_DESCRIPTOR is sent to the OS and the process is ended. Thus,the OS regards the target as operating normally and allows use of thetarget.

The process described above is executed, whereby use of uncalled-fordevices is forbidden in accordance with the connection permission list.The connection device restriction device monitors aUSB_DEVICE_DESCRIPTOR request from the OS and, on detection of therequest, executes the above process. If error is notified at the time ofconnection, the OS does not establish connection with the target, sothat the target remains unusable thereafter.

Thus, with the connection device restriction device, restriction on useof devices can be set as desired so as to match the mode of operation,and since it is unnecessary to modify the processes executed by the OSand the target USB device, the restriction device can be easily appliedto existing systems.

In the foregoing is described the case where restriction is placed onconnection devices connected to USB ports. The present invention canalso be applied to restriction of connection devices connected to othertypes of connection port, such as an IEEE1394 port.

Also, in the above description, the PC uses the connection permissionlist as a common list. The PC may alternatively set user accounts forrespective users so that the users may use their respective accounts. Inthis case, connection permission lists are prepared for the respectiveuser accounts such that restrictions on use of devices are set for therespective users.

FIG. 7 shows the configuration of a connection device restriction deviceaccording to another embodiment, wherein the restriction device hasconnection permission lists prepared for respective user accounts.

The connection device restriction device 310 has a connection permissionlist 311 which is used in common for all users, a user-specificconnection permission list (for user 1) 312, a user-specific connectionpermission list (for user 2) 313, and a connection restriction unit 314.In the illustrated example, a permission list setting unit 350 forsetting the connection permission lists is provided externally to theconnection device restriction device 310. Further, a setting file updatedetermination unit 340 and a connection permission list selector 320 areadditionally provided. The functions of the connection permission listselector 320, setting file update determination unit 340 and permissionlist setting unit 350 are accomplished by causing a computer, in whichthe connection device restriction device 310 is incorporated, to executethe connection device restriction program or a related interfaceprogram.

The connection permission list 311 of the connection device restrictiondevice 310 is used in common for all users and is looked up by theconnection restriction unit 314 regardless of user account. Theconnection permission list (for user 1) 312 and the connectionpermission list (for user 2) 313 are selected in accordance with useraccounts and are looked up by the connection restriction unit 314.

The connection permission list selector 320 detects the account of auser who logged on by a logon process 330 of the OS, selects thecorresponding connection permission list, and notifies the connectionrestriction unit 314 of the selected list. During a logoff process ofthe OS, the selector 320 instructs the connection restriction unit 314to deselect the connection permission list which has been selected untilthen.

When updating of a connection permission list by a setting tool,described later, is detected, the setting file update determination unit340 notifies the permission list setting unit 350 that the connectionpermission list has been updated. An update instruction mayalternatively be generated by the administrator who updated theconnection permission list.

On detection of updating of a setting file, the permission list settingunit 350 updates the corresponding connection permission list.

Operation of the connection device restriction device 310 will be nowdescribed.

In a default state at the start of the PC, no user-specific connectionpermission list is selected by the connection permission list selector320, and the connection restriction unit 314 executes the deviceconnection restriction process by using the connection permission list(for common use) 311.

When a user account is set in the logon process 330 of the OS, aconnection permission list for user n (the list 312 for user 1 or thelist 313 for user 2) which corresponds to the account of the logged-onuser is selected by the connection permission list selector 320. Theconnection restriction unit 314 then performs the device connectionrestriction process by using the selected connection permission list(the list 312 for user or the list 313 for user 2) and the connectionpermission list (for common use) 311.

On execution of a logoff process of the OS, the connection permissionlist for user n (the list 312 for user 1 or the list 313 for user 2)which corresponds to the account of the logged-off user is deselected bythe connection permission list selector 320. The connection restrictionunit 314 then performs the device connection restriction process byusing only the connection permission list (for common use) 311.

Thus, in response to logon and logoff, a different connection permissionlist is selected and deselected, whereby restriction on use of devicescan be set differently depending on the user.

The following describes the manner of updating a connection permissionlist.

Using the setting tool, the administrator sets a connection permissionlist, whereupon the setting file update determination unit 340automatically detects the setting of the list or is notified of thesetting by the administrator, and then outputs a permission list updateinstruction to the permission list setting unit 350. The permission listsetting unit 350 stores the updated permission list in the correspondinglist memory of the connection device restriction device 310. Inaccordance with the updated connection permission list, the connectionrestriction unit 314 performs the device connection restriction process.

In the case where the updated permission list forbids the connection ofan already permitted device, the OS is restarted to forbid theconnection of the device. For example, the permission list setting unit350 detects the need for restart of the OS and displays an appropriatemessage on the monitor to urge the user to restart the OS.

The setting tool will be now described with reference to FIG. 8exemplifying a setting tool screen according to the embodiment.

The setting tool screen 401 has a field 402 for selecting a setting file(connection permission list) to be updated, and a user selection field403 for selecting all users or a specific user as target user(s). Theadministrator who is to make changes sets a setting file to be updatedas well as target users, and presses a “Register devices to bepermitted” button 404 to proceed to the next step of the settingprocess.

If the “Register devices to be permitted” button 404 is thus pressedwith a target setting file and target users specified, the screenswitches to a screen for registering devices whose connection is to bepermitted.

FIG. 9 exemplifies such a registration screen according to theembodiment, which is displayed to allow registration of devices whoseconnection is to be permitted.

First, on the device registration screen 405, a device type to which thetarget device belongs is selected (in the illustrated example, thedevice types include USB, FDD (Floppy (registered trademark) DiskDrive), IEEE1394, and Serial/Parallel). In the following description, itis assumed that the USB 406 is selected.

When the USB 406 is selected, a “Permit all devices” option 407, a“Forbid all devices” option 408 and a “Permit specified devices” option409 for setting devices to be permitted are displayed as exceptioninformation items. If the option “Permit all devices” 407 is selected,the exception information is set such that connection of all USB devicesis permitted. On the other hand, if the option “Forbid all devices” 408is selected, the exception information is set such that connection ofall USB devices is forbidden. If the option “Permit specified devices”409 is selected, a “Specified devices” field 410 is displayed in whichis shown a list of devices currently set in the selected setting file.By rewriting the “Specified devices” field 410, it is possible to modifythe settings of permitted devices. In the illustrated example, thesetting “All HID devices” has been entered, and in this case, theexception information is set accordingly.

Further, when a USB device is added to the connection permission list,an “Add USB device” screen, for example, is displayed to facilitate thedesignation of the device. FIG. 10 exemplifies such an “Add USB device”screen according to the embodiment.

The “Add USB device” screen 411 has a “Specify unique ID” field 412 forentering a device unique ID to set a permitted device, a “Specify devicetype” field 413 for specifying a device type, and a “Specify from amongconnected devices” field 414 for specifying a device from among thecurrently connected devices. The administrator may use theeasiest-to-use field to specify a device.

As described above, each device setting screen has a screen forspecifying a device whose connection is to be permitted, and the screenfor specifying a device provides a method whereby a device can be mostuniquely specified according to its capability. In the case of a USBdevice, for example, the device is specified by its vendor ID/productID/serial number. To facilitate the setting, the device specifyingscreen also provides a method whereby a device type can be specified.For example, HID devices or the like, which are less likely to causesecurity problems, may be specified by category so that connection ofall devices falling under the category may be permitted. In addition,the device specifying screen provides a method whereby a device can bespecified from among the currently connected devices.

In the above description, the embodiment is applied to USB devices.Where the OS has a Plug-and-Play (hereinafter PnP) mechanism, forexample, use of devices may be restricted by intervening in themessaging procedure at the start of the computer or at the time a PnPdevice is plugged.

The following describes the case of restricting use of devices inWindows 2000/XP (registered trademark).

At the start of the computer or at the time a PnP device is plugged, thePnP manager of the OS sends out an IRP_MJPNP/IRP_MN_START_DEVICErequest. In response to the request, each device driver starts to usethe corresponding device. Accordingly, the connection device restrictiondevice is arranged on a route where the restriction device can receiveall IRP_MJPNP/IRP_MN_START_DEVICE requests.

The connection device restriction device receives eachIRP_MJPNP/IRP_MN_START_DEVICE request and acquires information wherebythe uniqueness of the corresponding device can be checked. In the caseof a USB device, for example, the information to be acquired includesUSB_DEVICE_DESCRIPTOR, USB_CONFIGURATION_DESCRIPTOR, andUSB_STRING_DESCRIPTOR containing the serial number.

Then, the information acquired from the target device is collated withthe connection permission list to determine whether or not the acquiredinformation is included in the list. If the list includes the acquiredinformation, the process is advanced in the regular way. Namely, theIRP_MJPNP/IRP_MN_START_DEVICE is returned intact to the OS as if therewas no intervention, whereupon the use of the device is started. On theother hand, if the information acquired from the target device is notincluded in the connection permission list, “failure” is returned, as areturned value, in response to the IRP_MJPNP/IRP_MN_START_DEVICErequest. Consequently, the device fails to be started and remainsunusable thereafter.

The process described above can be performed by a computer. In thiscase, a program is prepared in which is described the process forperforming the function of the connection device restriction device. Theprogram is executed by a computer, whereupon the aforementionedprocessing function is accomplished by the computer. The programdescribing the required process may be recorded on a computer-readablerecording medium. The computer-readable recording medium includes amagnetic recording device, an optical disc, a magneto-optical recordingmedium, a semiconductor memory, etc. The magnetic recording device maybe a hard disk drive (HDD), a flexible disk (FD), a magnetic tape or thelike. As the optical disc, a DVD (Digital Versatile Disc), a DVD-RAM(Random Access Memory), a CD-ROM (Compact Disc Read Only Memory), a CD-R(Recordable)/RW (ReWritable) or the like may be used. Themagneto-optical recording medium includes an MO (Magneto-Optical disk)etc.

To market the program, portable recording media, such as DVDs andCD-ROMs, on which the program is recorded may be put on sale.Alternatively, the program may be stored in the storage device of aserver computer and may be transferred from the server computer to othercomputers via a network.

A computer which is to execute the program stores in its storage devicethe program recorded on a portable recording medium or transferred fromthe server computer, for example. Then, the computer loads the programfrom its storage device and performs processing in accordance with theprogram. The computer may load the program directly from the portablerecording medium to perform the process in accordance with the program.Also, as the program is transferred from the server computer, thecomputer may sequentially perform the process in accordance with thereceived program.

According to the present invention, when a connection device isconnected to a connection port, device information is acquired from theconnection device and is collated with the connection permission list todetermine whether or not the connection device corresponds to anyconnection-permitted device defined in the list. Connection of theconnection device is permitted only if the connection device is aconnection-permitted device. In the connection permission list,specification items for specifying connection-permitted devices, such asdevice types, device designations and user designations, can be set asneeded. This enables the administrator to set desired restrictiveconditions matching the mode of operation, to restrict use of connectiondevices which users are allowed to use. Also, by setting requiredspecification items defining connection-permitted devices in theconnection permission list, it is possible to prevent the use ofuncalled-for devices, thereby enhancing the security.

The foregoing is considered as illustrative only of the principles ofthe present invention. Further, since numerous modifications and changeswill readily occur to those skilled in the art, it is not desired tolimit the invention to the exact construction and applications shown anddescribed, and accordingly, all suitable modifications and equivalentsmay be regarded as falling within the scope of the invention in theappended claims and their equivalents.

1. A recording medium storing a program that causes a computer toexecute a procedure, the procedure comprising: permitting setting of avendor identifier (ID) commonly assigned to a plurality of devices whichare to be permitted to connect with the computer for use by selectingdevice information obtained from a device connected to the computer;determining, upon acquisition of a vendor ID from a connection deviceconnected to the computer storing the program, whether the acquiredvendor ID is identical to the set vendor ID; and restricting use of theconnection device according to a result of the determining.
 2. Therecording medium according to claim 1, wherein the program causes thecomputer to restrict use of another connection device connected to thecomputer, as well as the use of the connection device connected to thecomputer.
 3. A recording medium storing a program that causes a computerto execute a procedure, the procedure comprising: permitting setting ofa product identifier (ID) commonly assigned to a plurality of deviceswhich are to be permitted to connect with the computer for use byselecting device information obtained from a device connected to thecomputer; determining, upon acquisition of a product ID from aconnection device connected to the computer storing the program, whetherthe acquired product ID is identical to the set product ID; andrestricting use of the connection device according to a result of thedetermining.
 4. The recording medium according to claim 3, wherein theprogram causes the computer to restrict use of another connection deviceconnected to the computer, as well as the use of the connection deviceconnected to the computer.
 5. A restriction method of restricting use ofa connection device connected to a computer, comprising: setting avendor identifier (ID) in the computer according to an operation ofsetting the vendor ID commonly assigned to a plurality of devices whichare to be permitted to connect with the computer for use by selectingdevice information obtained from a device connected to the computer;determining, upon acquisition of a vendor ID from the connection deviceconnected to the computer, whether the acquired vendor ID is identicalto the set vendor ID; and restricting the use of the connection deviceaccording to a result of the determining.
 6. A restriction method ofrestricting use of a connection device connected to a computer,comprising: setting a product identifier (ID) in the computer accordingto an operation of setting the product ID commonly assigned to aplurality of devices which are to be permitted to connect with thecomputer for use by selecting device information obtained from a deviceconnected to the computer; determining, upon acquisition of a product IDfrom the connection device connected to the computer, whether theacquired product ID is identical to the set product ID; and restrictingthe use of the connection device according to a result of thedetermining.
 7. A computer to which a device can be connected, thecomputer comprising: a unit which permits setting of a vendor identifier(ID) commonly assigned to a plurality of devices which are to bepermitted to connect with the computer for use by selecting deviceinformation obtained from a device connected to the computer; a memorywhich stores the set vendor ID; a determination unit which, uponacquisition of a vendor ID from a connection device connected to thecomputer, accesses the memory to determine whether the acquired vendorID is identical to the set vendor ID; and an execution unit whichrestricts use of the connection device according to a result of thedetermination.
 8. A computer to which a device can be connected, thecomputer comprising: a unit which permits setting of a productidentifier (ID) commonly assigned to a plurality of devices which are tobe permitted to connect with the computer for use by selecting deviceinformation obtained from a device connected to the computer; a memorywhich stores the set product ID; a determination unit which, uponacquisition of a product ID from a connection device connected to thecomputer, accesses the memory to determine whether the acquired productID is identical to the set product ID; and an execution unit whichrestricts use of the connection device according to a result of thedetermination.
 9. A computer comprising: a connection port whichconnects a connection device to the computer; a monitor which displays avendor identifier (ID) allowable for connection to the computer,according to an operation of setting the vendor ID commonly assigned toa plurality of devices which are to be permitted to connect with thecomputer for use by selecting device information obtained from a deviceconnected to the computer; and a memory which stores the set vendor ID,wherein, upon acquisition of a vendor ID from the connection deviceconnected to the computer, it is determined by accessing the memorywhether the acquired vendor ID is identical to the set vendor ID, anduse of the connection device is restricted according to a result of thedetermination.
 10. A computer comprising: a connection port whichconnects a connection device to the computer; a monitor which displays aproduct identifier (ID) allowable for connection to the computer,according to an operation of setting the product ID commonly assigned toa plurality of devices which are to be permitted to connect with thecomputer for use by selecting device information obtained from a deviceconnected to the computer; and a memory which stores the set product ID,wherein, upon acquisition of a product ID from the connection deviceconnected to the computer, it is determined by accessing the memorywhether the acquired product ID is identical to the set product ID, anduse of the connection device is restricted according to a result of thedetermination.